home *** CD-ROM | disk | FTP | other *** search
- Notes about chat sequences
- --------------------------
-
- With chat strings, the following escape sequences are recognised in both
- expect and send strings:
-
- \\ as \
- \" as " (double quote)
- \a as bell (7)
- \b as backspace (8)
- \t as tab (9)
- \n as linefeed, (10)
- \v as vertical tab (11)
- \f as form feed (12)
- \r as carriage return, (13)
- \e as escape (27)
-
- The strings must be in pairs, of which the first string is an expect
- string.
-
- Expect strings are currently case sensitively matched against ALL
- received characters that are NOT part of a VT100 escape sequence
- (except the initial ESC characater), including control characters.
-
- Expect strings may be specified as "" for a null string, though
- currently this equates to any character, rather than send the following
- send string immediately.
-
- Send strings may be specified as "" null string. This may be used to ensure
- two separate, and possibly separated string matches are done before a
- send string is sent.
-
- Expect/Send pairs need not be enclosed in quotes, unless the string
- includes a space character, or is a null string.
-
- No additional characaters are appended to send strings, to if you want
- an EOL in the send string, you must specfiy it, eg "\r\n".
-
- The chat handler works in parellel with user input, thus pressing keys
- one the keyboard, or keypad will have their usual effect. If local echo,
- or line edit mode is being used, entered characters are treated as part of
- the received character stream.
-
- The maximum length of a expect string is currently 16 characters.
-
- Not all of the above may suit everyone, but at least you know how it
- behaves, and thus what to expect from it.
-
- I may, at some time, extend the string handling to allow optional
- case-insenstive matching, optional filtering of control characters from
- received stream, inclusion of \x00 type escape sequences, pause delays,
- timeouts and embed terminal switch commands in send strings, eg for
- switching a spool on/off.
-
- ---
-
- * A note about !TCPIP command parsing: Older versions of !TCPIP could
- accept upto 10 separate tokens per command. I am not sure what maximum
- command length was acceptable, though I think it was 80 or charcters
- including end of line and string terminator.
-
- In order to cope with terminal switch tokens, net, terminal and chat
- command separators, chat strings etc, the maximum number of tokens has
- now been increased to 64, and the command line length in the command
- box at the top of terminal windows is now 1020 characters (allowing for
- "\r\n\0" to be appended.
-
- Maximum in-window, (ie at the prompt) command line length is from the
- prompt to the end of the line, ie variable.
-
-